home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
qbbs
/
dinfavt4.zip
/
DINFOAVT.DOC
next >
Wrap
Text File
|
1993-01-15
|
9KB
|
210 lines
╒══════════════════════════════════════════════════════════════════╕
│ DINFOAVT 4; RemoteAccess 1.xx ANSI/AVATAR DORINFO1.DEF utility │
╘══════════════════════════════════════════════════════════════════╛
Dinfoavt.Exe/Dinfoavt.Doc written by geoffrey booher 1:2270/233.1@fidonet
Copyright (c) 1990 - 1993; boo s/w development hq
disclaimer:
───────────
DINFOAVT 4 is *ONLY* guaranteed to consume diskspace. It has been very
extensively tested and found to be pretty reliable. In no way is the
Author of this program responsible for any damages, consequential, or
otherwise from the neglect of DINFOAVT 4's use or misuse. DINFOAVT 4
is provided as is, without warranty of any kind, either expressed or implied.
DINFOAVT 4 may be distributed freely subject to the following conditions:
1. No fees are charged for distributing or obtaining the DINFOAVT files.
DINFAVT4.ZIP may be placed on pay/subscription systems, provided that
a fee is not charged for DINFAVT4.ZIP itself.
2. The files within the DINFAVT4 archive are not modified in ANY way, this
includes reprocessing/recompressing the DINFAVT4.ZIP to another type
of compression.
questions:
──────────
Send Netmail to geoffrey booher, 1:2270/233.0@fidonet. Or I suppose any
questions you have could be addressed to me in the RA_UTIL conference.
files in the archive:
─────────────────────
DINFOAVT.EXE - 80386 protect mode version of the program, this file is ready
to use if you have a 386 or higher based CPU machine.
DINFOAVT.XT - 808X version of the program, rename to DINFOAVT.EXE and use
this file if you have a 286 or below based CPU machine.
DINFOAVT.DOC - You're reading it.
WHATSNEW.4 - History and new features in DINFOAVT 4.
README.1ST - Notice about the distribution archive.
overview and features:
──────────────────────
DINFOAVT+ 4 is a DORINFO1.DEF utility specifically for use with
RemoteAccess 1.xx.
It's main purpose is to change the DORINFO1.DEF file if the user online has
BOTH ANSI/AVATAR emulation enabled to plain ANSI so software that does not
recognise the new 2 and 3 DORINFO1.DEF codes can still do ANSI if possible.
I wrote this program because my users that are taking advantage of my AVATAR
screens were complaining there was 'no colors' on 'DOORS' and other Type 7
programs I run. So ... I figured that these dudes were running the code '3'
in DORINFO1.DEF that they were using ANSI and AVATAR both. If that was the
case, then temporarily change to code '1' ANSI to run the door, and restore
the ANSI/AVATAR code '3' after the door. Simple enough.
Page 2
setting up DINFOAVT 4:
──────────────────────
Put the correct Dinfoavt.Exe anywhere in your DOS PATH, along with any of
your other utilities.
DINFOAVT Command line parameters:
DINFOAVT
DINFOAVT /? - Shows a help screen.
DINFOAVT /I - Use this switch going INTO the door. It will look for a
DORINFO?.DEF file (yes, it will use DORINFO1, DORINFO2, etc)
in the CURRENT DIRECTORY. If line 10 is '2' or '3', AVATAR or
ANSI/AVATAR, it will write a DORINFO?.$$$ file with the
original DORINFO?.DEF contents, and change the DORINFO?.DEF
file to '1' on line 10 for ANSI if ANSI/AVATAR is detected. It
will change the DORINFO?.DEF to '0' if AVATAR alone is detected.
If it's 0 - ASCII/TTY; or 1 - ANSI only, it won't update
the DORINFO?.DEF file, and won't create the DORINFO?.$$$ file.
DINFOAVT /O - Use this switch on the way OUT the door. It will look for the
DORINFO?.$$$ if it was created by the DINFOAVT /I option.
If it doesn't find it, it assumes ANSI/AVATAR both was NOT the
initial emulation and will do nothing. If it finds the
DORINFO?.$$$ file, it will overwrite it with the CURRENT
DORINFO?.DEF file, and then rewrite a new DORINFO?.DEF file
with updated time remaining, etc from the door, and change
line 10 back to '3' so ANSI/AVATAR is enabled again upon return
to the BBS. This is NOT needed by RemoteAccess, but may be
by other programs following in a batchfile.
DINFOAVT /IO - This switch just changes DORINFO1.DEF and does not attempt to
change DORINFO1.DEF back when the DOOR is done. Some DOORS
use DORINFO1.DEF to get some settings like graphics, but RA
actually uses EXITINFO.BBS to update the time used.
DINFOAVT /R - This switch adds the -R info to the line settings info if a
"reliable" (error-free) connection is active. If you do not
have an error-correcting modem, then this parameter is of no
use to you. Example of what DINFOAVT /R will do :
14400 BAUD-R,N,8,1 (the -R is added in if error-free connect)
2400 BAUD,N-8-1 (-R is NOT added if not error-free)
DINFOAVT reads the EXITINFO.BBS file in the current directory
to determine if the connection is error-free.
NOTE: Not all doors support the -R in DORINFO1.DEF, but some
of the newer filedoors do. Doors that don't support
it really don't care, so the -R won't hurt, as the door
will only read just the speed number.
DINFOAVT /D - This switch displays the contents of the DORINFO?.DEF file.
Page 3
using DINFOAVT 4:
─────────────────
You will need to create a batchfile to run your door. Here's an example:
Type 7 - Optional Data: *C /C C:\RA\BBSLIST.BAT *M *N
Bbslist.Bat: -OR-
@Echo OFF @Echo OFF
Dinfoavt /I /R Dinfoavt /IO /R
Bbslist Bbslist.Cfg Bbslist Bbslist.Cfg
Dinfoavt /O
I realise making batchfiles to run type 7's is not the most elegant way to
run things, but DINFOAVT 4 is really a kludge program to give ANSI Colors
AT LEAST in your doors until such time the doors become AVATAR 'smart'. It
is also VERY handy to pass error-correcting status to those doors that
support the -R in DORINFO1.DEF.
DINFOAVT+ 4 technical info:
───────────────────────────
Dinfoavt.Cpp was written in C language with the CPlusPlus extension option.
Dinfoavt.Exe was compiled with Borland International's Borland C++ 3.1 using
the Small Memory Module ( < 64kb heap ).
DINFOAVT.EXE has the following errorlevels:
Errorlevel 4 - invalid parameter or no parameters (help screen)
Errorlevel 3 - DORINFO1.DEF successfully updated
Errorlevel 2 - File I/O error
Errorlevel 1 - Missing DORINFO?.DEF or EXITINFO.BBS (/R option)
Errorlevel 0 - DORINFO1.DEF not changed
NOTE!! DINFOAVT 4 expects to find ONE DORINFO?.DEF file in the CURRENT
DIRECTORY! If you are running a multi-line system, this should not
pose a problem as the door will likely be executed in that nodes
directory. The RemoteAccess documentation states doors must be run
from their own seperate directories when running multiple copies, so
DINFOAVT 4 should find the correct DORINFO1.DEF file in the
directory currently in. if you rename it to DORINFO2.DEF in your
batchfile - that is okay - DINFOAVT will support that too.
If the program finds more than ONE DORINFO?.DEF file in the current
directory it will use the first one it finds, whether valid or not!
Page 4
thanks:
───────
Thanks to andrew milner and the RemoteAccess beta duders for the best BBS
software available anywhere hands down. :-)
Thanks to Kevin Zimmerman at The Boomtown BBS - 1:2270/868@fidonet for
sometimes getting 7 versions of my programs per day to pre-test out.
Thanks to Bruce Bodger at The Truckstop BBS - 1:170/400@fidonet for helping
out with beta bashing some of my stuff.
Thanks to Bob R. at The Anonymous BBS - 1:154/40@fidonet for some good
suggestions for DINFOAVT 2.00 and 4 (the /R command). :-)
Thanks to Mark Howard at Rivendell TAP/NA - 1:260/340@fidonet for writing
RAEXIT for RemoteAccess 1.00 EXITINFO.BBS conversion. It was his program
that gave me the idea for the display contents (/d) command and helped test
if the /R command worked properly.
misc:
─────
The following products/examples are the Copyrighted materials of their
respective named holders:
DINFOAVT 4 boo s/w development hq
Borland C++ 3.1 Borland International
RemoteAccess andrew milner and Continental Software
BBSLIST Off The Wall Programming
AVATAR George A. Stanislav
Fidonet Tom Jennings